fix(db): complete artifact intent insert acl - #148
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
INSERTgrant forv2_artifact_upload_intents.quiesced_atto the single clean baselineWhy
Drizzle emits the nullable
quiesced_atcolumn asDEFAULTwhen reserving an artifact upload. PostgreSQL therefore requires column-level insert permission even though application code omits the field. Production logs showed this exact permission failure after the preceding ownership-query corrections.Production application
The grant and the one-row Drizzle baseline checksum were updated atomically under the database maintenance advisory lock. The production ledger still contains exactly one migration row.
Verification
app_agentcan insertquiesced_atapp_agentstill cannot update the table broadlypnpm typecheck:scriptspnpm turbo lintpnpm --filter @cheatcode/db db:generatereports no schema changes